ARGOBENTO002 (VSL_DISCHARGE_BENTO

ARGOBENTO002 (VSL_DISCHARGE_BENTO_PROCESSING)

This setting is to specify where vessel discharge decking requests are processed and where vessel discharges are executed.

We recommend applying the value for this setting at the Global level.

Valid values are:

XPS_SERVER: This is the default value to use the legacy functionality. In this case, the XPS server handles vessel discharge decking requests and executes vessel discharges.
XPS_SERVER_WITH_XD: To use a Scaled N4 XD service to handle vessel discharge decking requests, but have XPS still execute vessel discharges. This option reduces the load on the XPS server for larger terminal operations.
N4 (default): When this option is selected, vessel discharge decking requests are executed by N4. This option further reduces the load on the XPS server.However, if you experience performance issues, you can choose to roll it back to XPS_Server. See Rolling back N4 move processing to XPS (on page 1).

When Scaled XD clients are not available, XPS accepts the Scaled XD decking requests. However, this is based on the value set for the N4 setting ARGOXPS013 (XPS_ACCEPTS_SCALED_XD_DECKING_REQUESTS).

If ARGOXPS013 = True:

Scaled XD decking requests will be sent to the XPS server if Scaled XD clients are not available.

If ARGOXPS013 = False:

Decking requests are not sent to XPS, which means that the container will not be decked.

If the containers in the decking request have a valid planned position, that is from pre-decking, the planned position is retained.

If the containers in the decking request do not have a planned position, the containers will fail to deck. In the case of a gate transaction, XPS will not create a plan for the fail to deck containers. However, the gate transaction will be moved into Trouble status, depending on the gate configuration.